home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Collection of Internet
/
Collection of Internet.iso
/
infosrvr
/
dev
/
www_talk.930
/
001270_daemon _Mon Jun 14 11:16:26 1993.msg
< prev
next >
Wrap
Internet Message Format
|
1994-01-24
|
3KB
Received: by nxoc01.cern.ch (NeXT-1.0 (From Sendmail 5.52)/NeXT-2.0)
id AA27368; Mon, 14 Jun 93 11:16:29 MET DST
Return-Path: <dsr@hplb.hpl.hp.com>
Received: from dxmint.cern.ch by nxoc01.cern.ch (NeXT-1.0 (From Sendmail 5.52)/NeXT-2.0)
id AA27364; Mon, 14 Jun 93 11:16:26 MET DST
Received: from hplb.hpl.hp.com by dxmint.cern.ch (5.65/DEC-Ultrix/4.3)
id AA19579; Mon, 14 Jun 1993 11:38:27 +0200
Received: from dragget.hpl.hp.com by hplb.hpl.hp.com; Mon, 14 Jun 93 10:30:38 +0100
Received: by manuel.hpl.hp.com
(16.6/15.6+ISC) id AA00563; Mon, 14 Jun 93 10:36:42 +0100
From: Dave_Raggett <dsr@hplb.hpl.hp.com>
Message-Id: <9306140936.AA00563@manuel.hpl.hp.com>
Subject: HTML+ support for eqn & Postscript
To: torben@hawaii.edu, janssen@parc.xerox.com
Date: Mon, 14 Jun 93 10:36:40 BST
Cc: www-talk@nxoc01.cern.ch
Mailer: Elm [revision: 66.36.1.1]
Torben Nielsen says:
> I realize this has come up before, but how about really doing something about
> equation support? There are lots of documents I would like to put into the
> Web, but without support for embedded equations, it's really quite difficult.
> Something simple like eqn support would be great. And eqn shouldn't be all
> that hard to parse either.....
Bill Janssen chips in with:
> And I really like to send encapsulated Postcript in my documents...
> Having ghostscript should make the parsing and layout easy!
Well both of these will be possible with the HTML+ DTD, by using the capability
to embed foreign formats inline in the HTML+ source, e.g.
<H2>A example of an equation</H2>
<EMBED TYPE="text/eqn">zeta (s) ~=~ sum from k=1 to inf
k sup -s ~~~ (Re s > 1) </EMBED>
The browser identifies the format of the embedded data from the "type"
attribute, specified as a MIME content type. Certain characters need to
be escaped using entity definitions, e.g. ">" by ">" in the example.
Building in support for a range of formats has the danger of leading to
very large programs for browsers. This could be avoided by using a common
API for rendering foreign formats, e.g. as functions that take a sequence
of bytes and return a pixmap.
Browsers can then be upgraded to display new formats without changing their
code at all. All you would need is a way of binding the MIME content type
to the function name for that format, e.g. via X resources or a config file.
The functions could be implemented as separate programs driven via pipes and
stdin/stdout or as dynamically linked library modules (Windows DLLs).
How does that sound?
Dave
p.s. you can also put the foreign data in a separate file referenced by a URL.